home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Shareware Overload Trio 2
/
Shareware Overload Trio Volume 2 (Chestnut CD-ROM).ISO
/
dir40
/
pm_10_94.zip
/
STUFF.DOC
< prev
Wrap
Text File
|
1994-10-12
|
3KB
|
46 lines
Greetings, Tran (a.k.a. Thomas Pytel) here. This is version 3.04 of PMODE,
my protected mode DOS extender. It is publicly available and is not
confidential or proprietary. I, Thomas Pytel, reserve all rights to the source
code. However, feel free to use or distribute them in any manner you wish. All
I ask, if you use this code in some production, is credits.
This package is meant mainly as an update for coders already using PMODE,
But you can use it to start from scratch. The code and documentation may not
be thoroughly clear, in this case if you need more examples get some of the
other PMODE releases (like PMC or any demo source codes I have released) for
more practical examples.
------------------------------------------------------------------------------
Oh well, another update... A single little buggy has been squashed. Also I
have added low level access to the PMODE internal real and protected mode
stacks. This should help you save a few K of low memory if you do your own
low level mode switching by allowing your stacks to share memory with PMODE's
protected mode callback and real mode call stacks.
For those of you who use PMC... Thanx to someone out there for pointing out
to me that TASM used 16bit addressing to access a certain variable. I went to
fix it, but discovered that this was a bigger problem than I at first thought,
as BCC32 seems to access external word variables with 16bit addressing. With
all the PMC code (startup and libs) that would have to be fixed up (well, I'm
exaggerating a bit here, it would not take long really), I do not wish to deal
with this now since I have projects of my own. And fix it for what? Just so
BCC32 can screw it up anyway?!? But there is a slightly good side to this all,
if the size of the _DATA + _BSS segments does not exceed 64k, all will be
well. If anyone out there with enough experience feels like it, feel free to
go through the code yourself and fix it (and release it). If you do this, keep
in mind to compile the library routines that are in C to assembly and check
for these 16bit addressing errors there.
------------------------------------------------------------------------------
This file is dated as of October 12, 1994. Enjoy protected mode. You can
send me mail, but I can not reply due to the fact that I do not have real
Inet access (tell me about all the nice bugs you find). I'm just waiting for
this account to die, but as of now it is still around - tran@phantom.com.
Oh well...
Tran...